Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm working in an environment where setting and retrieving objects to/from cache can be somewhat complex, and I want to handle caching of table metadata in a way that is not easily done with the available cache adapter mechanism.
Currently, our adapter has to parse the $key string to identify which type data we're caching (ie. table meta data) which is a pretty brittle solution and does not support future cached components such as the Model.
If we were able to extend the Table class, we could override some of the methods (such as the get_meta_data method) to customize them to meet our caching needs.
By adding the "make_table" factory method, we are able to able to subclass the Table class without affecting the rest of the calls to Table::load().